BACKGROUND: We have 2 computers. Both are running Windows 7. One works fine all the time. No problems with Internet access, other than slow response. The configuration includes: Toshiba computer with a Tealtek RTL819SE wireless card, communication to a D-Link DIR-655 wireless router and a Qwest Actiontec GT701 modem The failure only occurs with the DSL service, modem and Wireless Router configuration here at our winter home in Arizona. We do not have a failure at our other home in the state of Washington. FAILURE CONDITION: Internet access is lost intermittently. Internet Explorer displays a message, “Internet Explorer cannot display the webpage.” Also, a line is displayed allowing a selection to diagnose the problem. A window is opened to detect the problem. When testing is completed, the following message is displayed: “The DNS server isn’t responding”. OBSERVATION 1: Checking the modem processor status shows there are two DNS servers. Using the Ping command both DNS servers reply correctly. OBSERVATION 2: Next, command NSLOOKUP was executed along with the DNS addresses entered on the command line. The request times out and the message “*** request to unknown timed-out.” The same message is displayed when the modem address, 192.168.0.1 is entered. OBSERVATION 3: Next, an IPCONFIG /RELEASE command was executed and failed with the following message:”No operation can be performed on Wireless Network Connection 2 while its media is disconnected. OBSERVATION 4: A similar message was displayed when an IPCONFIG /RENEW command was executed. OBSERVATION 5: Last, the wireless router cannot be accessed. (this tends make me think the failure is computer software related.) OBSERVATION 6: One other symptom: When IPCONFIG is executed many messages similar to: C:\Users\Bob>IPCONFIG Windows IP Configuration Wireless LAN adapter Wireless Network Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : domain.actdsltmp Link-local IPv6 Address . . . . . : fe80::2192:aada:7ef5:9025%30 IPv4 Address. . . . . . . . . . . : 172.168.0.198 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 172.168.0.1 Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : domain.actdsltmp Tunnel adapter Reusable Microsoft 6To4 Adapter: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 12: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix. : domain.actdsltmp Tunnel adapter Reusable Microsoft 6To4 Adapter: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix. : Tunnel adapter Local Area Connection* 12: Note: The “Tunnel adapter” messages listed most number values from 9 up to 25. The problem seems to clear after about 30 or 45 minutes. QUESTIONS: Q-1: Based on the Internet Explorer message, how can a use identify the DNS address having the failure? Q-2: Is there a “user corrective action” available to restore the DNS communication failure? Q-3: What conditions allow the DNS failure to correct its self? Q-4: Why are all the “Tunnel adapter” type messages by IPCONFIG displayed? Q-5: Can the “Tunnel adapter” type messages be eliminated?

You've got a discrepancy here: you said your router is a 192.169.0.1 but your IPCONFIG has it set to 172.168.0.1; that's an issue if true. To answer your questions - 1) Based on the IE message, no. The error is a failure to contact a DNS server, any DNS server; in this case, probably your router. 2) Yes, reset the router. 3) The computer reconnecting to the router. 4) Don't let it bother you, it's normal. E) Maybe. Try disabling IPv6. Can you post an IPCONFIG /ALL from both the working and wacked-out machines? This will allow us to see which DNS servers they're connecting to. It should be the router in both cases, but it may not be.

Hi, The issue is caused by network. Let's reset WinSock and update the network card drivers to check the result. Reset WinSock ------------------- Open the cmd with Administrator privilege and type the following command: netsh winsock reset catalog Also, the following article should be helpful. http://www.anetforums.com/posts.aspx?ThreadIndex=28415 Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. If the issue persists, please try the Clean Boot and disable any Security software temporarily. Regards, SimidaPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, The issue is caused by network. Let's reset WinSock and update the network card drivers to check the result. Reset WinSock ------------------- Open the cmd with Administrator privilege and type the following command: netsh winsock reset catalog Also, the following article should be helpful. http://www.anetforums.com/posts.aspx?ThreadIndex=28415 Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. If the issue persists, please try the Clean Boot and disable any Security software temporarily. Regards, SimidaPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, The issue is caused by network. Let's reset WinSock and update the network card drivers to check the result. Reset WinSock ------------------- Open the cmd with Administrator privilege and type the following command: netsh winsock reset catalog Also, the following article should be helpful. http://www.anetforums.com/posts.aspx?ThreadIndex=28415 Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. If the issue persists, please try the Clean Boot and disable any Security software temporarily. Regards, SimidaPlease remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thank you for the help. TCP/IPv6 is disabled. TCP/IPv4 has been changed to us specific DNS server IP addresses. No problems have occurred since making this change. Oh, the wireless router is 172.168.0.1 and the modem is 192.168.0.1. Does that cause any problems? Should TCP/IPv6 be enabled by listing the DNS server addresses?

No, you don't need IPv6 enabled. Yes, setting the DNS to the modem's (sorry, I misread your original post) address would cause this very issue because the modem doesn't act as a forwarder, while the router does. Since you've got it working, don't bother changing anything now, but the correct way to set it up would be to enter the ISP's DNS server addresses into the router's configuration (on its Internet Settings or WAN page) and then set your machine's DNS to the router (this is usually done by the DHCP from the router anyway). DNS requests are sent to the router, which then forwards them to whatever servers are in its config. By adding the DNS servers directly to the Windows settings your computers will now always seek out those specific DNS servers regardless of where they're connected from. This shouldn't be an issue unless your ISP is strange, because a DNS server should accept a connection from anywhere. It may, however, cause a problem if you want to do any peer sharing between your computers.

Simida_W I downloaded the Winsock fix program and it does not say it is compatible with Windows 7. Therefore, the program was not executed at this time.

Bob Reese, Thank you for the reply. I like the suggestion. Since we move the computer between 2 locations, the router fix sounds better. However, there must be something else different in this computer because our other computer never had a DNS problem and

Bob Reese OK here are 2 ipconfig printouts save using CMD. Any thoughts as to why the one on the computer I generally us is so different. Ipconfig used to be a great tool for checking on Internet connections. With the large list on this computer it become nearly worthless. Your help is greatly appreciated. First is from the laptop that does not have DNS problems: Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Sharon>ipconfig Windows IP Configuration Wireless LAN adapter Wireless Network Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : domain.actdsltmp Link-local IPv6 Address . . . . . : fe80::f46a:2666:729d:c05%12 IPv4 Address. . . . . . . . . . . : 172.168.0.197 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 172.168.0.1 Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Reusable Microsoft 6To4 Adapter: Connection-specific DNS Suffix . : domain.actdsltmp IPv6 Address. . . . . . . . . . . : 2002:aca8:c5::aca8:c5 Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301 Tunnel adapter isatap.domain.actdsltmp: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : domain.actdsltmp Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:18ec:24c2:479d:7b79 Link-local IPv6 Address . . . . . : fe80::18ec:24c2:479d:7b79%13 Default Gateway . . . . . . . . . : Tunnel adapter isatap.{4D1ADE61-11B3-4892-BDF6-BC5C96341732}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter 6TO4 Adapter: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter isatap.{F3C71A5F-8E53-4712-9AC5-78ABAA4FF6BE}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : C:\Users\Sharon> ========================================= Next is an ipconfig executed on the computer with the DNS problem. Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Bob>ipconfig Windows IP Configuration Wireless LAN adapter Wireless Network Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : domain.actdsltmp IPv4 Address. . . . . . . . . . . : 172.168.0.198 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 172.168.0.1 Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : domain.actdsltmp Tunnel adapter Reusable Microsoft 6To4 Adapter: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 12: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 9: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:3cfa:5a0:479d:7b79 Link-local IPv6 Address . . . . . : fe80::3cfa:5a0:479d:7b79%13 Default Gateway . . . . . . . . . : Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter 6TO4 Adapter: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 15: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 14: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 13: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 16: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter isatap.domain.actdsltmp: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 17: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 23: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 21: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 18: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 19: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 20: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 24: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 22: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 25: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection* 26: Connection-specific DNS Suffix . : domain.actdsltmp IPv6 Address. . . . . . . . . . . : 2002:aca8:c6::aca8:c6 Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301 Tunnel adapter isatap.{127FEC4C-4150-4D46-ADE9-88B83D2FAD60}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : ===========================================

Yeah, I'll agree that the Tunnel Adapter creation is overkill and something that needs to be looked into by Microsoft. It seems to happen whenever a connection fails (in this case probably to your DNS server) and when it reconnects, instead of reusing an existing instance it creates a new one. And the old ones are almost impossible to get rid of. But this happened in Vista too, so it's not a Windows 7 thing. Anyway, an IPCONFIG by itself isn't going to show us any DNS- or DHCP-specific information; to get that you'll need to use an IPCONFIG /ALL and on the machine with all those Tunnel Adapters that's going to be a lot of irrelevant output, so feel free to just cut that stuff away. I would also recommend going to Realtek's website and downloading the latest drivers for your card. Don't use the ones from Windows Update or Toshiba's site as both of those are old versions (I couldn't find any chip on their site with that number, are you sure you typed it correctly?)